Resource configuration method, terminal device, and network device

ABSTRACT

Embodiments of this application relate to a resource configuration method, a terminal device, and a network device. The method includes: determining a frequency domain offset between a plurality of transmission resource chunks allocated by a network device, where the frequency domain offset is a frequency domain offset between a first transmission resource chunk and a second transmission resource chunk, and the first transmission resource chunk and the second transmission resource chunk are any two consecutive resource chunks on an uplink transmission in the plurality of transmission resource chunks; and determining the plurality of transmission resource chunks according to the frequency domain offset, wherein the plurality of transmission resource chunks are configured for a frequency hopping transmission.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of and claims priority toInternational Patent Application No. PCT/CN2017/109149, filed on Nov. 2,2017, the contents of which is hereby incorporated by reference in itsentirety.

BACKGROUND OF THE INVENTION Technical Field

This application relates to the communications field, and in particular,to a resource configuration method, a terminal device, and a networkdevice.

Related Art

In a Long Term Evolution (LTE) system, frequency domain frequencyhopping is introduced for uplink transmission (for example, physicaluplink shared channel (PUSCH) transmission), mainly to achieve twoobjectives: a current terminal device can obtain a frequency domaindiversity gain; and interference of another terminal device or cell israndomized.

However, if a similar LTE design is still used in a PUSCH design of anew radio (NR) system, there are the following disadvantages: frequencydomain resources depending on a frequency hopping function arefragmented, and scheduling of a base station is very complex. Inaddition, NR differs from an LTE system, in that densities and locationsof demodulation reference signals (DMRS) of different terminal devicesmay be different. Therefore, if a random frequency hopping manner isused, different terminal devices may perform sending at a same location,and it is very difficult to ensure that DMRS ports are orthogonal.

SUMMARY OF THE INVENTION

This application provides a resource configuration method, a terminaldevice, and a network device, so that the terminal device may obtain afrequency domain diversity gain and transmission resource fragmentationis avoided.

According to a first aspect, a resource configuration method isprovided. The method includes: determining a frequency domain offsetbetween a plurality of transmission resource chunks allocated by anetwork device, where the frequency domain offset is a frequency domainoffset between a first transmission resource chunk and a secondtransmission resource chunk, and the first transmission resource chunkand the second transmission resource chunk are any two resource chunksadjacent to each other in time domain in the plurality of transmissionresource chunks; and determining the plurality of transmission resourcechunks according to the frequency domain offset.

Therefore, according to the resource configuration method in thisembodiment of this application, the terminal device determines afrequency domain offset between any two neighboring transmissionresource chunks of the plurality of transmission resource chunksallocated by the network device, and determines the frequency domainlocation of the plurality of transmission resource chunks according tothe frequency domain offset. In this configuration manner, scheduling ofthe network device is simple, the terminal device may obtain a frequencydomain diversity gain, and transmission resource fragmentation isavoided.

With reference to the first aspect, in an implementation of the firstaspect, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

Correspondingly, the second transmission resource chunk is an (evennumber)th transmission resource chunk when the plurality of transmissionresource chunks is sorted in a time order.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thefrequency domain offset is a difference between a start location of thefirst transmission resource chunk in frequency domain and a startlocation of the second transmission resource chunk in frequency domain.

Optionally, the frequency domain offset may alternatively be adifference between an end location occupied by the first transmissionresource chunk in frequency domain and the start location occupied bythe second transmission resource chunk in frequency domain.

Optionally, the frequency domain offset may alternatively be adifference between a center location of a frequency domain resourceoccupied by the first transmission resource chunk and a center locationof a frequency domain resource occupied by the second transmissionresource chunk.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thefirst transmission resource chunk and the second transmission resourcechunk separately occupy a subframe or a mini-subframe; or the firsttransmission resource chunk occupies a first part of a subframe and thesecond transmission resource chunk occupies a second part of thesubframe; or the first transmission resource chunk occupies a first partof a mini-subframe and the second transmission resource chunk occupies asecond part of the mini-subframe.

It should be understood that when the first transmission resource andthe second transmission resource separately occupy two parts of asubframe or a mini-subframe, the two parts may be equal or unequal.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thedetermining a frequency domain offset between a plurality oftransmission resource chunks allocated by a network device includesreceiving the frequency domain offset sent by the network device.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thereceiving the frequency domain offset sent by the network deviceincludes: receiving a first configuration message sent by the networkdevice, where the first configuration message is used to indicate thefrequency domain offset, and the first configuration message is at leastone of a network broadcast message, a network system message, a RadioResource Control (RRC) message, a Media Access Control control element(MAC CE), and downlink control information (DCI).

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, themethod further includes: determining a resource area parameter, wherethe resource area parameter is used to indicate a frequency domain rangethat can be occupied by at least one transmission resource chunk of theplurality of transmission resource chunks, and the at least onetransmission resource chunk includes the first transmission resourcechunk or the second transmission resource chunk.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thedetermining a resource area parameter includes receiving the resourcearea parameter sent by the terminal device.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thereceiving the resource area parameter sent by the terminal deviceincludes: receiving a second configuration message sent by the terminaldevice, where the second configuration message is used to indicate theresource area parameter, and the second configuration message is atleast one of a network broadcast message, a network system message, anRRC message, a MAC CE, and DCI.

With reference to the first aspect and the foregoing implementations ofthe first aspect, in another implementation of the first aspect, thefrequency domain range that can be occupied by the at least onetransmission resource chunk and that is indicated by the resource areaparameter is discontinuous.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter may alternatively be continuous.

Therefore, according to the resource configuration method in thisembodiment of this application, the terminal device determines afrequency domain offset between any two neighboring transmissionresource chunks of the plurality of transmission resource chunksallocated by the network device, and may further determine the frequencydomain range that can be occupied by at least one transmission resourcechunk of the plurality of transmission resource chunks, and determinesthe frequency domain location of the plurality of transmission resourcechunks according to the frequency domain offset and the frequency domainrange that can be occupied. In this configuration manner, scheduling ofthe network device is simple, the terminal device may obtain a frequencydomain diversity gain, and transmission resource fragmentation isavoided.

According to a second aspect, a resource configuration method isprovided. The method includes: determining a frequency domain offsetbetween a plurality of transmission resource chunks allocated to aterminal device, where the frequency domain offset is a frequency domainoffset between a first transmission resource chunk and a secondtransmission resource chunk, and the first transmission resource chunkand the second transmission resource chunk are any two resource chunksadjacent to each other in time domain in the plurality of transmissionresource chunks; and sending the frequency domain offset to the terminaldevice.

Therefore, according to the resource configuration method in thisembodiment of this application, the network device configures theplurality of transmission resource chunks for uplink transmission of theterminal device, and sends the frequency domain offset between any twoneighboring transmission resource chunks of the plurality oftransmission resource chunks to the terminal device, so that theterminal device can determine the frequency domain location of theplurality of transmission resource chunks according to the frequencydomain offset. Therefore, a configuration manner of the network deviceis simple, the terminal device may obtain a frequency domain diversitygain, and transmission resource fragmentation is avoided.

With reference to the second aspect, in an implementation of the secondaspect, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

With reference to the second aspect and the foregoing implementations ofthe second aspect, in another implementation of the second aspect, thefrequency domain offset is a difference between a start location of thefirst transmission resource chunk in frequency domain and a startlocation of the second transmission resource chunk in frequency domain.

With reference to the second aspect and the foregoing implementations ofthe second aspect, in another implementation of the second aspect, thefirst transmission resource chunk and the second transmission resourcechunk separately occupy a subframe or a mini-subframe; or the firsttransmission resource chunk occupies a first part of a subframe and thesecond transmission resource chunk occupies a second part of thesubframe; or the first transmission resource chunk occupies a first partof a mini-subframe and the second transmission resource chunk occupies asecond part of the mini-subframe.

With reference to the second aspect and the foregoing implementations ofthe second aspect, in another implementation of the second aspect, thesending the frequency domain offset to the terminal device includes:sending a first configuration message to the terminal device, where thefirst configuration message is used to indicate the frequency domainoffset, and the first configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

With reference to the second aspect and the foregoing implementations ofthe second aspect, in another implementation of the second aspect, themethod further includes: sending a resource area parameter to theterminal device, where the resource area parameter is used to indicate afrequency domain range that can be occupied by at least one transmissionresource chunk of the plurality of transmission resource chunks, and theat least one transmission resource chunk includes the first transmissionresource chunk or the second transmission resource chunk.

With reference to the second aspect and the foregoing implementations ofthe second aspect, in another implementation of the second aspect, thesending a resource area parameter to the terminal device includes:sending a second configuration message to the terminal device, where thesecond configuration message is used to indicate the resource areaparameter, and the second configuration message is at least one of anetwork broadcast message, a network system message, an RRC message, aMAC CE, and DCI.

With reference to the second aspect and the foregoing implementations ofthe second aspect, in another implementation of the second aspect, thefrequency domain range that can be occupied by the at least onetransmission resource chunk and that is indicated by the resource areaparameter is discontinuous.

Therefore, according to the resource configuration method in thisembodiment of this application, the network device configures theplurality of transmission resource chunks for uplink transmission of theterminal device, sends the frequency domain offset between any twoneighboring transmission resource chunks of the plurality oftransmission resource chunks to the terminal device, and may furtherconfigure a frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks for the terminal device, so that the terminal device candetermine the frequency domain location of the plurality of transmissionresource chunks according to the frequency domain offset and thefrequency domain range that can be occupied. Therefore, a configurationmanner of the network device is simple, the terminal device may obtain afrequency domain diversity gain, and transmission resource fragmentationis avoided.

According to a third aspect, a resource configuration method isprovided. The method includes: determining a resource area parameter,where the resource area parameter is used to indicate a frequency domainrange that can be occupied by at least one transmission resource chunkof a plurality of transmission resource chunks allocated by a networkdevice; and determining the plurality of transmission resource chunksaccording to the resource area parameter.

Therefore, according to the resource configuration method in thisembodiment of this application, the terminal device determines theresource area parameter, where the resource area parameter is used toindicate the frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks allocated by the network device, and determines the plurality oftransmission resource chunks in the range indicated by the resource areaparameter, so that the terminal device may perform uplink transmissionby using the plurality of transmission resource chunks, to improvetransmission efficiency.

With reference to the third aspect, in an implementation of the thirdaspect, the determining a resource area parameter includes receiving theresource area parameter sent by the terminal device.

With reference to the third aspect and the foregoing implementations ofthe third aspect, in another implementation of the third aspect, thereceiving the resource area parameter sent by the terminal deviceincludes: receiving a configuration message sent by the terminal device,where the configuration message is used to indicate the resource areaparameter, and the configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

With reference to the third aspect and the foregoing implementations ofthe third aspect, in another implementation of the third aspect, thefrequency domain range that can be occupied by the at least onetransmission resource chunk and that is indicated by the resource areaparameter is discontinuous.

According to a fourth aspect, a resource configuration method isprovided. The method includes: determining a resource area parameter ofa terminal device, where the resource area parameter is used to indicatea frequency domain range that can be occupied by at least onetransmission resource chunk of a plurality of transmission resourcechunks allocated to the terminal device; and sending the resource areaparameter to the terminal device.

Therefore, according to the resource configuration method in thisembodiment of this application, the network device configures theplurality of transmission resource chunks for the terminal device, andsends, to the terminal device, the resource area parameter used toindicate the frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks, so that the terminal device can determine the plurality oftransmission resource chunks in the range indicated by the resource areaparameter, and perform uplink transmission by using the plurality oftransmission resource chunks, to improve transmission efficiency.

With reference to the fourth aspect, in an implementation of the fourthaspect, the sending the resource area parameter to the terminal deviceincludes: sending a configuration message to the terminal device, wherethe configuration message is used to indicate the resource areaparameter, and the configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

With reference to the fourth aspect and the foregoing implementations ofthe fourth aspect, in another implementation of the fourth aspect, thefrequency domain range that can be occupied by the at least onetransmission resource chunk and that is indicated by the resource areaparameter is discontinuous.

According to a fifth aspect, a terminal device is provided, configuredto perform the method according to the first aspect or any possibleimplementation of the first aspect. Specifically, the terminal deviceincludes units configured to perform the method according to the firstaspect or any possible implementation of the first aspect.

According to a sixth aspect, a network device is provided, configured toperform the method according to the second aspect or any possibleimplementation of the second aspect. Specifically, the network deviceincludes units configured to perform the method according to the secondaspect or any possible implementation of the second aspect.

According to a seventh aspect, a terminal device is provided, configuredto perform the method according to the third aspect or any possibleimplementation of the third aspect. Specifically, the terminal deviceincludes units configured to perform the method according to the thirdaspect or any possible implementation of the third aspect.

According to an eighth aspect, a network device is provided, configuredto perform the method according to the fourth aspect or any possibleimplementation of the fourth aspect. Specifically, the network deviceincludes units configured to perform the method according to the fourthaspect or any possible implementation of the fourth aspect.

According to a ninth aspect, a terminal device is provided, including astorage unit and a processor. The storage unit is configured to store aninstruction, the processor is configured to execute the instructionstored by the memory, and when the processor executes the instructionstored by the memory, the execution enables the processor to perform themethod according to the first aspect or any possible implementation ofthe first aspect.

According to a tenth aspect, a network device is provided, including astorage unit and a processor. The storage unit is configured to store aninstruction, the processor is configured to execute the instructionstored by the memory, and when the processor executes the instructionstored by the memory, the execution enables the processor to perform themethod according to the second aspect or any possible implementation ofthe second aspect.

According to an eleventh aspect, a terminal device is provided,including a storage unit and a processor. The storage unit is configuredto store an instruction, the processor is configured to execute theinstruction stored by the memory, and when the processor executes theinstruction stored by the memory, the execution enables the processor toperform the method according to the third aspect or any possibleimplementation of the third aspect.

According to a twelfth aspect, a network device is provided, including astorage unit and a processor. The storage unit is configured to store aninstruction, the processor is configured to execute the instructionstored by the memory, and when the processor executes the instructionstored by the memory, the execution enables the processor to perform themethod according to the fourth aspect or any possible implementation ofthe fourth aspect.

According to a thirteenth aspect, a computer-readable medium isprovided, configured to store a computer program. The computer programincludes an instruction used to perform the method according to thefirst aspect or any possible implementation of the first aspect.

According to a fourteenth aspect, a computer-readable medium isprovided, configured to store a computer program. The computer programincludes an instruction used to perform the method according to thesecond aspect or any possible implementation of the second aspect.

According to a fifteenth aspect, a computer-readable medium is provided,configured to store a computer program. The computer program includes aninstruction used to perform the method according to the third aspect orany possible implementation of the third aspect.

According to a sixteenth aspect, a computer-readable medium is provided,configured to store a computer program. The computer program includes aninstruction used to perform the method according to the fourth aspect orany possible implementation of the fourth aspect.

According to a seventeenth aspect, a computer program product includingan instruction is provided. When the computer program product runs on acomputer, the computer performs the resource configuration methodaccording to the first aspect or any possible implementation of thefirst aspect. Specifically, the computer program product may run on theterminal device of the fifth aspect.

According to an eighteenth aspect, a computer program product includingan instruction is provided. When the computer program product runs on acomputer, the computer performs the resource configuration methodaccording to the second aspect or any possible implementation of thesecond aspect. Specifically, the computer program product may run on thenetwork device of the sixth aspect.

According to a nineteenth aspect, a computer program product includingan instruction is provided. When the computer program product runs on acomputer, the computer performs the resource configuration methodaccording to the third aspect or any possible implementation of thethird aspect. Specifically, the computer program product may run on theterminal device of the seventh aspect.

According to a twentieth aspect, a computer program product including aninstruction is provided. When the computer program product runs on acomputer, the computer performs the resource configuration methodaccording to the fourth aspect or any possible implementation of thefourth aspect. Specifically, the computer program product may run on thenetwork device of the eighth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic flowchart of a resource configuration methodaccording to an embodiment of this application;

FIG. 2 is a schematic diagram of time domain sizes occupied by a firsttransmission resource chunk and a second transmission resource chunkaccording to an embodiment of this application;

FIG. 3 is a schematic diagram of time domain sizes occupied by a firsttransmission resource chunk and a second transmission resource chunkaccording to another embodiment of this application;

FIG. 4 is a schematic diagram of time domain sizes occupied by a firsttransmission resource chunk and a second transmission resource chunkaccording to still another embodiment of this application;

FIG. 5 is a schematic diagram of a time domain offset according to anembodiment of this application;

FIG. 6 is a schematic diagram of a time domain resource that can beoccupied by at least one transmission resource chunk according to anembodiment of this application;

FIG. 7 is a schematic diagram of a time domain resource that can beoccupied by at least one transmission resource chunk according toanother embodiment of this application;

FIG. 8 is a schematic flowchart of a resource configuration methodaccording to another embodiment of this application;

FIG. 9 is a schematic flowchart of a resource configuration methodaccording to still another embodiment of this application;

FIG. 10 is a schematic flowchart of a resource configuration methodaccording to still another embodiment of this application;

FIG. 11 is a schematic chunk diagram of a terminal device according toan embodiment of this application;

FIG. 12 is a schematic chunk diagram of a network device according to anembodiment of this application.

FIG. 13 is a schematic chunk diagram of a terminal device according toanother embodiment of this application;

FIG. 14 is a schematic chunk diagram of a network device according toanother embodiment of this application;

FIG. 15 is a schematic chunk diagram of a terminal device according tostill another embodiment of this application;

FIG. 16 is a schematic chunk diagram of a network device according tostill another embodiment of this application;

FIG. 17 is a schematic chunk diagram of a terminal device according tostill another embodiment of this application; and

FIG. 18 is a schematic chunk diagram of a network device according tostill another embodiment of this application.

DETAILED DESCRIPTION OF THE INVENTION

The following describes the technical solutions in the embodiments ofthis application with reference to the accompanying drawings.

The technical solutions in the embodiments of this application may beapplied to various communications systems, for example, a global systemfor mobile communications (GSM) system, a code division multiple access(CDMA) system, a wideband code division multiple access (WCDMA) system,a general packet radio service (GPRS), an LTE system, an LTE frequencydivision duplex (FDD) system, LTE time division duplex (TDD), auniversal mobile telecommunications system (UMTS), a worldwideinteroperability for microwave access (WiMAX) communications system, anda future fifth-generation (5G) system or NR.

A terminal device in the embodiments of this application may be userequipment, an access terminal, a subscriber unit, a subscriber station,a mobile station, a mobile console, a remote station, a remote terminal,a mobile device, a user terminal, a terminal, a wireless communicationsdevice, a user agent, or a user apparatus. The terminal device may befurther a cellular phone, a cordless phone, a session initiationprotocol (SIP) phone, a wireless local loop (WLL) station, a personaldigital assistant (PDA), a handheld device having a wirelesscommunication function, a computing device or another processing deviceconnected to a wireless modem, an in-vehicle device, a wearable device,a terminal device in a future 5G network or a terminal device in afuture evolved public land mobile network (PLMN), or the like. This isnot limited in the embodiments of this application.

A network device in the embodiments of this application may be a deviceconfigured to communicate with a terminal device. The network device maybe a base transceiver station (BTS) in a GSM system or CDMA, or may bean NodeB (NB) in a WCDM system, or may be an evolved NodeB (eNB oreNodeB) in an LTE system, or may be a wireless controller in a cloudradio access network (CRAN) scenario, or the network device may be arelay station, an access point, an in-vehicle device, a wearable device,a network device in a future 5G network or a network device in a futureevolved PLMN network, or the like. This is not limited in theembodiments of this application.

FIG. 1 is a schematic flowchart of a resource configuration method 100according to an embodiment of this application. The method 100 may beperformed by a terminal device. As shown in FIG. 1, the method 100includes: S110: Determine a frequency domain offset between a pluralityof transmission resource chunks allocated by a network device, where thefrequency domain offset is a frequency domain offset between a firsttransmission resource chunk and a second transmission resource chunk,and the first transmission resource chunk and the second transmissionresource chunk are any two resource chunks adjacent to each other intime domain in the plurality of transmission resource chunks. S120:Determine the plurality of transmission resource chunks according to thefrequency domain offset.

Specifically, the network device configures the plurality oftransmission resource chunks for the terminal device. The plurality oftransmission resource chunks may be used by the terminal device totransmit a PUSCH, and each transmission resource chunk may occupydifferent time domain and frequency domain resources. The terminaldevice may determine the frequency domain offset between any two of theplurality of transmission resource chunks by using preconfiguration orreceiving the frequency domain offset sent by the network device. Thisembodiment of this application is not limited thereto.

Optionally, in an embodiment, the terminal device may determine thefrequency domain offset by using preconfiguration, for example, theterminal device configures a fixed threshold as the frequency domainoffset.

Optionally, in an embodiment, the terminal device may further receive afirst configuration message sent by the network device, where the firstconfiguration message is used to indicate the frequency domain offset,and the first configuration message may be at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI. For example, the terminal device receives an RRC message sentby the network device, where the RRC message may include the frequencydomain offset. For another example, the terminal device receives an RRCmessage and a MAC CE sent by the network device, and determines, byusing the RRC message and the MAC CE, the frequency domain offsetconfigured by the network device.

In this embodiment of this application, time domain resource sizesoccupied by the plurality of transmission resource chunks allocated bythe network device to the terminal device may be the same or different,and a time domain size occupied by each of the plurality of transmissionresource chunks is not limited herein. Herein, any two transmissionresource chunks adjacent to each other in time domain in the pluralityof transmission resource chunks is used as an example, a time domainsize that may be occupied by each of the plurality of transmissionresource chunks is described with reference to FIG. 2 to FIG. 4, and theoccupied frequency domain size may be any size. The any two transmissionresource chunks adjacent to each other in time domain are a firsttransmission resource chunk and a second transmission resource chunk.

It should be understood that adjacent means that the first transmissionresource chunk and the second transmission resource chunk are adjacentto each other in time domain when the plurality of transmission resourcechunks of the terminal device are sorted according to a time order, butthe two transmission resource chunks may be continuous or discontinuousin time domain. For example, the first transmission resource chunk maybe an (odd number)th transmission resource chunk of the plurality oftransmission resource chunks when the plurality of transmission resourcechunks is sorted in a time order, but the second transmission resourcechunk is an (even number)th transmission resource chunk after the firsttransmission resource chunk.

Optionally, in an embodiment, the first transmission resource chunk andthe second transmission resource chunk may separately occupy two partsin a subframe, or may separately occupy two parts in a mini-subframe.For example, as shown in FIG. 2, the first transmission resource chunkoccupies a first part of a subframe K. The first part is the left partin FIG. 2, that is, the left black part in FIG. 2 is the firsttransmission resource chunk. The second transmission resource chunkoccupies a second part of the subframe K. The second part is the rightpart in FIG. 2, that is, the right black part in FIG. 2 is the secondtransmission resource chunk. Alternatively, as shown in FIG. 2, thesubframe K may also be a mini-subframe K. That is, the firsttransmission resource chunk occupies a first part of the mini-subframeK, and the second transmission resource chunk occupies a second part ofthe mini-subframe K.

It should be understood that, the first part and the second part may beequal in time domain, for example, a subframe or a mini-subframe may beequally divided by the first part and the second part; or the first partand the second part may be unequal. This embodiment of this applicationis not limited thereto.

Optionally, in an embodiment, the first transmission resource chunk andthe second transmission resource chunk may separately occupy a subframe,or may separately occupy a mini-subframe, where the subframe or themini-subframe is continuous. For example, as shown in FIG. 3, the firsttransmission resource chunk occupies a left subframe K in FIG. 3, andthe second transmission resource chunk occupies a right subframe K+1 inFIG. 3; or the first transmission resource chunk occupies the leftmini-subframe K in FIG. 3, and the second transmission resource chunkoccupies the right mini-subframe K+1 in FIG. 3. The subframe or themini-subframe occupied by the first transmission resource chunk and thesecond transmission resource chunk is continuous.

Optionally, in an embodiment, the first transmission resource chunk andthe second transmission resource chunk may separately occupy a subframe,or may separately occupy a mini-subframe, where the subframe or themini-subframe is discontinuous. For example, as shown in FIG. 4, thefirst transmission resource chunk occupies a left subframe M in FIG. 4,and the second transmission resource chunk occupies a right subframe Nin FIG. 4; or the first transmission resource chunk occupies the leftmini-subframe M in FIG. 4, and the second transmission resource chunkoccupies the right mini-subframe N in FIG. 4. The subframe or themini-subframe occupied by the first transmission resource chunk and thesecond transmission resource chunk is discontinuous, that is, adifference between M and N is greater than 1. Optionally, anothersubframe between the subframe M and the subframe N, or anothermini-subframe between the mini-subframe M and the mini-subframe N may bea transmission resource allocated by the network device to anotherterminal device. This embodiment of this application is not limitedthereto.

It should be understood that the subframe may be 1 ms and may include 14orthogonal frequency division multiplexing (OFDM) symbols.Correspondingly, the mini-subframe is less than the subframe, and themini-subframe may include less than 14 OFDM symbols.

For ease of description, a time domain size and a frequency domain sizeoccupied by the first transmission resource chunk and the secondtransmission resource chunk described below are not limited. That thefirst transmission resource chunk is before the second transmissionresource chunk in time domain is used as an example for description.

In this embodiment of this application, the terminal device maydetermine a frequency domain resource location occupied by the firsttransmission resource chunk, for example, may determine a frequencydomain location of the first transmission resource chunk according toconfiguration of the network device, determine the frequency domainoffset between the first transmission resource chunk and the secondtransmission resource chunk, and determine, according to the frequencydomain offset, a frequency domain resource location occupied by thesecond transmission resource chunk.

It should be understood that as shown in FIG. 5, a left black chunkindicates the first transmission resource chunk, a right black chunkindicates the second transmission resource chunk, and the frequencydomain offset (Poffset) may indicate a difference between the startlocation occupied by the first transmission resource chunk in frequencydomain and the start location occupied by the second transmissionresource chunk in frequency domain. The terminal device may determine,according to a sum of the start location occupied by the firsttransmission resource chunk in frequency domain and the frequency domainoffset, the start location occupied by the second transmission resourcechunk in frequency domain. Optionally, the frequency domain offset mayfurther indicate the frequency domain offset between the firsttransmission resource chunk and the second transmission resource chunkin another manner.

For example, the frequency domain offset may further indicate adifference between an end location occupied by the first transmissionresource chunk in frequency domain and the start location occupied bythe second transmission resource chunk in frequency domain. The terminaldevice may determine, according to a sum of the end location occupied bythe first transmission resource chunk in frequency domain and thefrequency domain offset, the start location occupied by the secondtransmission resource chunk in frequency domain.

For another example, the frequency domain offset may further indicate adifference between a center location of a frequency domain resourceoccupied by the first transmission resource chunk and a center locationof a frequency domain resource occupied by the second transmissionresource chunk. The terminal device may determine, according to a sum ofthe center location of the frequency domain resource occupied by thefirst transmission resource chunk and the frequency domain offset, thecenter location of the frequency domain resource occupied by the secondtransmission resource chunk, and may determine, according to a size ofthe second transmission resource chunk, a start location of thefrequency domain resource occupied by the second transmission resourcechunk.

In this embodiment of this application, the terminal device may furtherdetermine a resource area parameter, where the resource area parameteris used to indicate a frequency domain range that can be occupied by atleast one transmission resource chunk of the plurality of transmissionresource chunks allocated by the network device to the terminal device.Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter may be continuous or discontinuous, for example,may be a plurality of discrete areas.

It should be understood that the resource area parameter indicates thefrequency domain range that can be occupied by the at least onetransmission resource chunk, the at least one transmission resourcechunk may be some or all of the plurality of transmission resourcechunks, and the at least one transmission resource chunk includes atleast the second transmission resource chunk. Specifically, the terminaldevice may determine, according to preconfiguration or semi-static ordynamic configuration of the network device, the frequency domainlocation occupied by the first transmission resource chunk, and thendetermine the location of the second transmission resource chunkaccording to the frequency domain location occupied by the firsttransmission resource chunk and the frequency domain offset. Herein,that the resource area parameter indicates the frequency domain rangethat can be occupied by the second transmission resource chunk is usedas an example for description.

Optionally, in an embodiment, the frequency domain range that can beoccupied by the at least one transmission resource chunk and that isindicated by the resource area parameter may be continuous, that is, thefrequency domain range that can be occupied by the second transmissionresource chunk is continuous. For example, as shown in FIG. 6, theterminal device determines, according to the resource area parameter,that the frequency domain range that can be occupied by the secondtransmission resource chunk is a frequency domain range other than anedge slash shadow area on the right side, and the terminal devicedetermines the second transmission resource chunk in the area accordingto the first transmission resource chunk and the frequency domainoffset.

As shown in FIG. 6, an edge location indicated by the slash shadow areaon the right side is not used to transmit a PUSCH, but may be used totransmit another signal, for example, a physical uplink control channel(PUCCH).

Optionally, if it is determined, according to the first transmissionresource chunk and the frequency domain offset, that the range of thesecond transmission resource chunk exceeds the range indicated by theresource area parameter, as shown in FIG. 6, a part not exceeding therange indicated by the resource area parameter and a part exceeding therange indicated by the resource area parameter may be separated. Thepart exceeding the range indicated by the resource area parameter isplaced on another side for transmission by using a method of cycling inthe range indicated by the resource area parameter.

Optionally, in an embodiment, the frequency domain range that can beoccupied by the at least one transmission resource chunk and that isindicated by the resource area parameter may be discontinuous, that is,the frequency domain range that can be occupied by the secondtransmission resource chunk is discontinuous. For example, the areaindicated by the resource area parameter may be a plurality ofdiscontinuous areas. As shown in FIG. 7, the area indicated by theresource area parameter may include two areas, that is, an area 1 and anarea 2 indicated by cross-connected-line shadow areas in FIG. 7, and thesecond transmission resource chunk belongs to the area 1 and the area 2.

Specifically, the terminal device determines the second transmissionresource chunk in the area 1 and the area 2 according to the firsttransmission resource chunk and the frequency domain offset, where thefrequency domain offset may not include a part other than the area 1 andthe area 2. Similarly, when it is determined, according to the firsttransmission resource chunk and the frequency domain offset, that thestart location of the second transmission resource chunk is close to anedge of the area 1 or the area 2, and the second transmission resourcechunk has a part exceeding the area 1 or the area 2, the part exceedingthe area 1 or the area 2 and a part not exceeding the area 1 or the area2 in the second transmission resource chunk may also be separated, andcycle in the area 1 and/or the area 2. For example, it is determinedthat the start location of the second transmission resource chunk isclose to the edge of the area 2, and the second transmission resourcechunk has a part exceeding the area 2. The second transmission resourcechunk may be separated for transmission. The part exceeding the area 2may continue to be transmitted in a cycling manner in the area 2, or maybe transmitted in a cycling manner in all available areas, that is,cycles in the area 1 and the area 2, and the part exceeding the area 2in the second transmission resource chunk is mapped to the area 1. Thisembodiment of this application is not limited thereto.

In this embodiment of this application, the terminal device determinesthat the resource area parameter may be preconfigured. Optionally, theterminal device may further receive a second configuration message sentby the network device, where the second configuration message is used toindicate the resource area parameter, and the second configurationmessage is at least one of a network broadcast message, a network systemmessage, an RRC message, a MAC CE, and DCI. For example, the terminaldevice receives an RRC message sent by the network device, where the RRCmessage may include the resource area parameter. For another example,the terminal device receives an RRC message and a MAC CE sent by thenetwork device, and determines, by using the RRC message and the MAC CE,the resource area parameter configured by the network device.

Therefore, according to the resource configuration method in thisembodiment of this application, the terminal device determines afrequency domain offset between any two neighboring transmissionresource chunks of the plurality of transmission resource chunksallocated by the network device, and may further determine the frequencydomain range that can be occupied by at least one transmission resourcechunk of the plurality of transmission resource chunks, and determinesthe frequency domain location of the plurality of transmission resourcechunks according to the frequency domain offset and the frequency domainrange that can be occupied. In this configuration manner, scheduling ofthe network device is simple, the terminal device may obtain a frequencydomain diversity gain, and transmission resource fragmentation isavoided.

The foregoing describes the resource configuration method according tothe embodiments of this application in detail with reference to FIG. 1to FIG. 7 from the perspective of the terminal device, and the followingdescribes the resource configuration method according to the embodimentsof this application with reference to FIG. 8 from the perspective of anetwork device.

FIG. 8 is a schematic flowchart of a resource configuration method 200according to another embodiment of this application. The method 200 maybe performed by a network device. As shown in FIG. 8, the method 200includes: S210: Determine a frequency domain offset between a pluralityof transmission resource chunks allocated to a terminal device, wherethe frequency domain offset is a frequency domain offset between a firsttransmission resource chunk and a second transmission resource chunk,and the first transmission resource chunk and the second transmissionresource chunk are any two resource chunks adjacent to each other intime domain in the plurality of transmission resource chunks. S220: Sendthe frequency domain offset to the terminal device.

Optionally, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

Optionally, the frequency domain offset is a difference between a startlocation of the first transmission resource chunk in frequency domainand a start location of the second transmission resource chunk infrequency domain.

Optionally, the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; or optionally, the first transmission resource chunkoccupies a first part of a subframe and the second transmission resourcechunk occupies a second part of the subframe; or

Optionally, the first transmission resource chunk occupies a first partof a mini-subframe and the second transmission resource chunk occupies asecond part of the mini-subframe.

Optionally, the sending the frequency domain offset to the terminaldevice includes: sending a first configuration message to the terminaldevice, where the first configuration message is used to indicate thefrequency domain offset, and the first configuration message is at leastone of a network broadcast message, a network system message, an RRCmessage, a MAC CE, and DCI.

Optionally, the method further includes: sending a resource areaparameter to the terminal device, where the resource area parameter isused to indicate a frequency domain range that can be occupied by atleast one transmission resource chunk of the plurality of transmissionresource chunks, and the at least one transmission resource chunkincludes the first transmission resource chunk or the secondtransmission resource chunk.

Optionally, the sending the resource area parameter to the terminaldevice includes: sending second a configuration message to the terminaldevice, where the second configuration message is used to indicate theresource area parameter, and the second configuration message is atleast one of a network broadcast message, a network system message, anRRC message, a MAC CE, and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the network device in the method 200 inthis embodiment of this application may correspond to the network devicein the method 100, and the terminal device in the method 200 maycorrespond to the terminal device in the method 100. Details are notprovided herein again.

Therefore, according to the resource configuration method in thisembodiment of this application, the network device configures theplurality of transmission resource chunks for uplink transmission of theterminal device, sends the frequency domain offset between any twoneighboring transmission resource chunks of the plurality oftransmission resource chunks to the terminal device, and may furtherconfigure a frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks for the terminal device, so that the terminal device candetermine the frequency domain location of the plurality of transmissionresource chunks according to the frequency domain offset and thefrequency domain range that can be occupied. Therefore, a configurationmanner of the network device is simple, the terminal device may obtain afrequency domain diversity gain, and transmission resource fragmentationis avoided.

FIG. 9 is a schematic flowchart of a resource configuration method 300according to still another embodiment of this application. The method300 may be performed by a terminal device. As shown in FIG. 9, themethod 300 includes: S310: Determine a resource area parameter, wherethe resource area parameter is used to indicate a frequency domain rangethat can be occupied by at least one transmission resource chunk of aplurality of transmission resource chunks allocated by a network device.S320: Determine the plurality of transmission resource chunks accordingto the resource area parameter.

Specifically, the terminal device determines that the resource areaparameter may be preconfigured. Alternatively, the terminal device mayfurther receive a configuration message sent by the network device,where the configuration message is used to indicate the resource areaparameter, and the configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI. For example, the terminal device receives an RRC message sentby the network device, where the RRC message may include the resourcearea parameter. For another example, the terminal device receives an RRCmessage and a MAC CE sent by the network device, and determines, byusing the RRC message and the MAC CE, the resource area parameterconfigured by the network device.

In this embodiment of this application, the resource area parameterdetermined by the terminal device is used to indicate a frequency domainrange that can be occupied by at least one transmission resource chunkof the plurality of transmission resource chunks allocated by thenetwork device to the terminal device. The at least one transmissionresource chunk may be some or all of the plurality of transmissionresource chunks. Optionally, the frequency domain range that can beoccupied by the at least one transmission resource chunk and that isindicated by the resource area parameter may be continuous ordiscontinuous, for example, may be a plurality of discrete areas.

Optionally, in an embodiment, the frequency domain range that can beoccupied by the at least one transmission resource chunk and that isindicated by the resource area parameter may be continuous. For example,as shown in FIG. 6, the terminal device determines, according to theresource area parameter, that the frequency domain range that can beoccupied by the at least one transmission resource chunk may be anentire frequency domain range other than an edge slash shadow area onthe right side. As shown in FIG. 6, an edge location indicated by theslash shadow area on the right side is not used to transmit a PUSCH, butmay be used to transmit another signal, for example, a PUCCH.

Optionally, in an embodiment, the frequency domain range that can beoccupied by the at least one transmission resource chunk and that isindicated by the resource area parameter may be discontinuous. Forexample, the area indicated by the resource area parameter may be aplurality of discontinuous areas. As shown in FIG. 7, the area indicatedby the resource area parameter may include two areas, that is, an area 1and an area 2 indicated by a cross-connected-line shadow area in FIG. 7,that is, the at least one transmission resource chunk all belongs to thearea 1 and the area 2.

In this embodiment of this application, the terminal device maydetermine, according to the resource area parameter, the frequencydomain range that can be occupied by the at least one transmissionresource chunk of the plurality of transmission resource chunksallocated by the network device. For example, the terminal device mayperform uplink transmission in a frequency hopping manner, for example,transmit a PUSCH. The at least one transmission resource chunk includesat least a transmission resource chunk that needs to be transmitted in afrequency hopping manner.

Specifically, the terminal device may perform frequency hoppingtransmission in a manner in the prior art. For example, for any twoneighboring transmission resource chunks of the plurality oftransmission resource chunks configured by the network device, after afrequency domain location of a previous transmission resource chunk isfixed, a frequency domain location of a next transmission resource chunkmay be determined according to a frequency hopping function. The nexttransmission resource chunk belongs to the at least one transmissionresource chunk, that is, the frequency domain location occupied by thenext transmission resource chunk belongs to the frequency domain rangethat can be occupied by the at least one transmission resource chunk andthat is indicated by the resource area parameter.

Optionally, the terminal device may further determine the frequencydomain offset between any two neighboring transmission resource chunksin the manner of the method 100 and the method 200, to perform frequencyhopping transmission. Details are not provided herein. It should beunderstood that the terminal device determines the frequency domainrange that can be occupied and that is indicated by the resource areaparameter, and the terminal device determines the plurality oftransmission resource chunks in the range, and performs uplinktransmission by using the plurality of transmission resource chunks, forexample, transmits a PUSCH.

Therefore, according to the resource configuration method in thisembodiment of this application, the terminal device determines theresource area parameter, where the resource area parameter is used toindicate the frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks allocated by the network device, and determines the plurality oftransmission resource chunks in the range indicated by the resource areaparameter, so that the terminal device may perform uplink transmissionby using the plurality of transmission resource chunks, to improvetransmission efficiency.

The foregoing describes the resource configuration method according tothe embodiments of this application in detail with reference to FIG. 9from the perspective of the terminal device, and the following describesthe resource configuration method according to the embodiments of thisapplication with reference to FIG. 10 from the perspective of a networkdevice.

FIG. 10 is a schematic flowchart of a resource configuration method 400according to still another embodiment of this application. The method400 may be performed by a network device. As shown in FIG. 10, themethod 400 includes: S410: Determine a resource area parameter of aterminal device, where the resource area parameter is used to indicate afrequency domain range that can be occupied by at least one transmissionresource chunk of a plurality of transmission resource chunks allocatedto the terminal device. S420: Send the resource area parameter to theterminal device.

Optionally, the sending the resource area parameter to the terminaldevice includes: sending a configuration message to the terminal device,where the configuration message is used to indicate the resource areaparameter, and the configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the network device in the method 400 inthis embodiment of this application may correspond to the network devicein the method 300, and the terminal device in the method 400 maycorrespond to the terminal device in the method 300. Details are notprovided herein again.

Therefore, according to the resource configuration method in thisembodiment of this application, the network device configures theplurality of transmission resource chunks for the terminal device, andsends, to the terminal device, the resource area parameter used toindicate the frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks, so that the terminal device can determine the plurality oftransmission resource chunks in the range indicated by the resource areaparameter, and perform uplink transmission by using the plurality oftransmission resource chunks, to improve transmission efficiency.

It should be understood that sequence numbers of the foregoing processesdo not mean execution sequences in various embodiments of thisapplication. The execution sequences of the processes should bedetermined according to functions and internal logic of the processes,and should not be construed as any limitation on the implementationprocesses of the embodiments of this application.

In addition, the term “and/or” in this specification describes only anassociation relationship for describing associated objects andrepresents that three relationships may exist. For example, A and/or Bmay represent the following three cases: only A exists, both A and Bexist, and only B exists. In addition, the character “/” in thisspecification generally indicates an “or” relationship between theassociated objects.

The foregoing describes the resource configuration method according tothe embodiments of this application in detail with reference to FIG. 1to FIG. 10, and the following describes the terminal device and thenetwork device according to the embodiments of this application withreference to FIG. 11 to FIG. 18.

As shown in FIG. 11, a terminal device 500 according to an embodiment ofthis application includes: a determining unit 510, and optionally, mayfurther include a receiving unit 520.

Specifically, the determining unit 510 is configured to determine afrequency domain offset between a plurality of transmission resourcechunks allocated by a network device, where the frequency domain offsetis a frequency domain offset between a first transmission resource chunkand a second transmission resource chunk, and the first transmissionresource chunk and the second transmission resource chunk are any tworesource chunks adjacent to each other in time domain in the pluralityof transmission resource chunks; and the determining unit 510 is furtherconfigured to determine the plurality of transmission resource chunksaccording to the frequency domain offset.

Optionally, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

Optionally, the frequency domain offset is a difference between a startlocation of the first transmission resource chunk in frequency domainand a start location of the second transmission resource chunk infrequency domain.

Optionally, the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; or the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.

Optionally, the receiving unit 520 is configured to receive thefrequency domain offset sent by the network device.

Optionally, the receiving unit 520 is specifically configured to receivea first configuration message sent by the network device, where thefirst configuration message is used to indicate the frequency domainoffset, and the first configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the determining unit 510 is further configured to determinea resource area parameter, where the resource area parameter is used toindicate a frequency domain range that can be occupied by at least onetransmission resource chunk of the plurality of transmission resourcechunks, and the at least one transmission resource chunk includes thefirst transmission resource chunk or the second transmission resourcechunk.

Optionally, the receiving unit 520 is configured to receive the resourcearea parameter sent by the terminal device.

Optionally, the receiving unit 520 is specifically configured to receivea second configuration message sent by the network device, where thesecond configuration message is used to indicate the resource areaparameter, and the second configuration message is at least one of anetwork broadcast message, a network system message, an RRC message, aMAC CE, and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the terminal device 500 according to thisembodiment of this application may correspondingly perform the method100 in the embodiments of this application. The foregoing and otheroperations and/or functions of the units of the terminal device 500 areseparately used to implement the corresponding procedures of theterminal device in the methods in FIG. 1 to FIG. 8. For the purpose ofconciseness, details are not described herein again.

Therefore, the terminal device in this embodiment of this applicationdetermines a frequency domain offset between any two neighboringtransmission resource chunks of the plurality of transmission resourcechunks allocated by the network device, and may further determine thefrequency domain range that can be occupied by at least one transmissionresource chunk of the plurality of transmission resource chunks, anddetermines the frequency domain location of the plurality oftransmission resource chunks according to the frequency domain offsetand the frequency domain range that can be occupied. In thisconfiguration manner, scheduling of the network device is simple, theterminal device may obtain a frequency domain diversity gain, andtransmission resource fragmentation is avoided.

As shown in FIG. 12, a network device 600 according to an embodiment ofthis application includes: a determining unit 610 and a sending unit620.

Specifically, the determining unit 610 is configured to determine afrequency domain offset between a plurality of transmission resourcechunks allocated to a terminal device, where the frequency domain offsetis a frequency domain offset between a first transmission resource chunkand a second transmission resource chunk, and the first transmissionresource chunk and the second transmission resource chunk are any tworesource chunks adjacent to each other in time domain in the pluralityof transmission resource chunks; and the sending unit 620 is configuredto send the frequency domain offset to the terminal device.

Optionally, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

Optionally, the frequency domain offset is a difference between a startlocation of the first transmission resource chunk in frequency domainand a start location of the second transmission resource chunk infrequency domain.

Optionally, the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; or the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.

Optionally, the sending unit 620 is specifically configured to send afirst configuration message to the terminal device, where the firstconfiguration message is used to indicate the frequency domain offset,and the first configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the sending unit 620 is further configured to send aresource area parameter to the terminal device, where the resource areaparameter is used to indicate a frequency domain range that can beoccupied by at least one transmission resource chunk of the plurality oftransmission resource chunks, and the at least one transmission resourcechunk includes the first transmission resource chunk or the secondtransmission resource chunk.

Optionally, the sending unit 620 is specifically configured to send asecond configuration message to the terminal device, where the secondconfiguration message is used to indicate the resource area parameter,and the second configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the network device 600 according to thisembodiment of this application may correspondingly perform the method200 in the embodiments of this application. The foregoing and otheroperations and/or functions of the units of the network device 600 areseparately used to implement the corresponding procedures of the networkdevice in the methods in FIG. 1 to FIG. 8. For the purpose ofconciseness, details are not described herein again.

Therefore, the network device in this embodiment of this applicationconfigures the plurality of transmission resource chunks for uplinktransmission of the terminal device, sends the frequency domain offsetbetween any two neighboring transmission resource chunks of theplurality of transmission resource chunks to the terminal device, andmay further configure a frequency domain range that can be occupied byat least one transmission resource chunk of the plurality oftransmission resource chunks for the terminal device, so that theterminal device can determine the frequency domain location of theplurality of transmission resource chunks according to the frequencydomain offset and the frequency domain range that can be occupied.

Therefore, a configuration manner of the network device is simple, theterminal device may obtain a frequency domain diversity gain, andtransmission resource fragmentation is avoided.

As shown in FIG. 13, a terminal device 700 according to an embodiment ofthis application includes: a determining unit 710, and optionally, mayfurther include a receiving unit 720.

Specifically, the determining unit 710 is configured to determine aresource area parameter, where the resource area parameter is used toindicate a frequency domain range that can be occupied by at least onetransmission resource chunk of a plurality of transmission resourcechunks allocated by a network device; and the determining unit 710 isfurther configured to determine the plurality of transmission resourcechunks according to the resource area parameter.

Optionally, the receiving unit 720 is configured to receive the resourcearea parameter sent by the terminal device.

Optionally, the receiving unit 720 is specifically configured to receivea configuration message sent by the network device, where theconfiguration message is used to indicate the resource area parameter,and the configuration message is at least one of a network broadcastmessage, a network system message, an RRC message, a MAC CE, and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the terminal device 700 according to thisembodiment of this application may correspondingly perform the method300 in the embodiments of this application. The foregoing and otheroperations and/or functions of the units of the terminal device 700 areseparately used to implement the corresponding procedures of theterminal device in the methods in FIG. 9 and FIG. 10. For the purpose ofconciseness, details are not described herein again.

Therefore, the terminal device in this embodiment of this applicationdetermines the resource area parameter, where the resource areaparameter is used to indicate the frequency domain range that can beoccupied by at least one transmission resource chunk of the plurality oftransmission resource chunks allocated by the network device, anddetermines the plurality of transmission resource chunks in the rangeindicated by the resource area parameter, so that the terminal devicemay perform uplink transmission by using the plurality of transmissionresource chunks, to improve transmission efficiency.

As shown in FIG. 14, a network device 800 according to this embodimentof this application includes: a determining unit 810 and a sending unit820.

Specifically, the determining unit 810 is configured to determine aresource area parameter of a terminal device, where the resource areaparameter is used to indicate a frequency domain range that can beoccupied by at least one transmission resource chunk of a plurality oftransmission resource chunks allocated to the terminal device; and thesending unit 820 is configured to send the resource area parameter tothe terminal device.

Optionally, the sending unit 820 is specifically configured to send aconfiguration message to the terminal device, where the configurationmessage is used to indicate the resource area parameter, and theconfiguration message is at least one of a network broadcast message, anetwork system message, an RRC message, a MAC CE, and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the network device 800 according to thisembodiment of this application may correspondingly perform the method400 in the embodiments of this application. The foregoing and otheroperations and/or functions of the units of the network device 800 areseparately used to implement the corresponding procedures of the networkdevice in the methods in FIG. 9 and FIG. 10. For the purpose ofconciseness, details are not described herein again.

Therefore, the network device in this embodiment of this applicationconfigures the plurality of transmission resource chunks for theterminal device, and sends, to the terminal device, the resource areaparameter used to indicate the frequency domain range that can beoccupied by at least one transmission resource chunk of the plurality oftransmission resource chunks, so that the terminal device can determinethe plurality of transmission resource chunks in the range indicated bythe resource area parameter, and perform uplink transmission by usingthe plurality of transmission resource chunks, to improve transmissionefficiency.

FIG. 15 is a schematic chunk diagram of a terminal device 900 accordingto an embodiment of this application. As shown in FIG. 15, the terminaldevice 900 includes: a processor 910 and a transceiver 920, where theprocessor 910 and the transceiver 920 are connected. Optionally, theterminal device 900 further includes a memory 930, where the memory 930and the processor 910 are connected. The processor 910, the memory 930,and the transceiver 920 communicate with each other and transfer and/orcontrol a data signal through an internal connection path. The memory930 may be configured to store an instruction, and the processor 910 isconfigured to execute the instruction stored by the memory 930, tocontrol the transceiver 920 to send information or a signal. Theprocessor 910 is configured to: determine a frequency domain offsetbetween a plurality of transmission resource chunks allocated by anetwork device, where the frequency domain offset is a frequency domainoffset between a first transmission resource chunk and a secondtransmission resource chunk, and the first transmission resource chunkand the second transmission resource chunk are any two resource chunksadjacent to each other in time domain in the plurality of transmissionresource chunks; and determine the plurality of transmission resourcechunks according to the frequency domain offset.

Optionally, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

Optionally, the frequency domain offset is a difference between a startlocation of the first transmission resource chunk in frequency domainand a start location of the second transmission resource chunk infrequency domain.

Optionally, the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; or the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.

Optionally, the transceiver 920 is configured to receive the frequencydomain offset sent by the network device.

Optionally, the transceiver 920 is configured to receive a firstconfiguration message sent by the network device, where the firstconfiguration message is used to indicate the frequency domain offset,and the first configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the processor 910 is configured to determine a resource areaparameter, where the resource area parameter is used to indicate afrequency domain range that can be occupied by at least one transmissionresource chunk of the plurality of transmission resource chunks, and theat least one transmission resource chunk includes the first transmissionresource chunk or the second transmission resource chunk.

Optionally, the transceiver 920 is configured to receive the resourcearea parameter sent by the terminal device.

Optionally, the transceiver 920 is configured to receive a secondconfiguration message sent by the network device, where the secondconfiguration message is used to indicate the resource area parameter,and the second configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the terminal device 900 according to thisembodiment of this application may correspond to the terminal device 500in the embodiments of this application, and may correspond to acorresponding entity for performing the method 100 in the embodiments ofthis application. The foregoing and other operations and/or functions ofthe units of the terminal device 900 are separately used to implementthe corresponding procedures of the terminal device in the methods inFIG. 1 to FIG. 8. For the purpose of conciseness, details are notdescribed herein again.

Therefore, the terminal device in this embodiment of this applicationdetermines a frequency domain offset between any two neighboringtransmission resource chunks of the plurality of transmission resourcechunks allocated by the network device, and may further determine thefrequency domain range that can be occupied by at least one transmissionresource chunk of the plurality of transmission resource chunks, anddetermines the frequency domain location of the plurality oftransmission resource chunks according to the frequency domain offsetand the frequency domain range that can be occupied. In thisconfiguration manner, scheduling of the network device is simple, theterminal device may obtain a frequency domain diversity gain, andtransmission resource fragmentation is avoided.

FIG. 16 is a schematic chunk diagram of a network device 1000 accordingto an embodiment of this application. As shown in FIG. 16, the networkdevice 1000 includes: a processor 1010 and a transceiver 1020, where theprocessor 1010 and the transceiver 1020 are connected. Optionally, thenetwork device 1000 further includes a memory 1030, where the memory1030 and the processor 1010 are connected. The processor 1010, thememory 1030, and the transceiver 1020 communicate with each other andtransfer and/or control a data signal through an internal connectionpath. The memory 1030 may be configured to store an instruction, and theprocessor 1010 is configured to execute the instruction stored by thememory 1030, to control the transceiver 1020 to send information or asignal. The processor 1010 is configured to determine a frequency domainoffset between a plurality of transmission resource chunks allocated toa terminal device, where the frequency domain offset is a frequencydomain offset between a first transmission resource chunk and a secondtransmission resource chunk, and the first transmission resource chunkand the second transmission resource chunk are any two resource chunksadjacent to each other in time domain in the plurality of transmissionresource chunks; and the transceiver 1020 is configured to send thefrequency domain offset to the terminal device.

Optionally, the first transmission resource chunk is an (odd number)thtransmission resource chunk when the plurality of transmission resourcechunks is sorted in a time order, and the second transmission resourcechunk is located after the first transmission resource chunk in timedomain.

Optionally, the frequency domain offset is a difference between a startlocation of the first transmission resource chunk in frequency domainand a start location of the second transmission resource chunk infrequency domain.

Optionally, the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; or the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.

Optionally, the transceiver 1020 is configured to send a firstconfiguration message to the terminal device, where the firstconfiguration message is used to indicate the frequency domain offset,and the first configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the transceiver 1020 is configured to send a resource areaparameter to the terminal device, where the resource area parameter isused to indicate a frequency domain range that can be occupied by atleast one transmission resource chunk of the plurality of transmissionresource chunks, and the at least one transmission resource chunkincludes the first transmission resource chunk or the secondtransmission resource chunk.

Optionally, the transceiver 1020 is configured to send a secondconfiguration message to the terminal device, where the secondconfiguration message is used to indicate the resource area parameter,and the second configuration message is at least one of a networkbroadcast message, a network system message, an RRC message, a MAC CE,and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the network device 1000 according to thisembodiment of this application may correspond to the network device 600in the embodiments of this application, and may correspond to acorresponding entity for performing the method 200 in the embodiments ofthis application. The foregoing and other operations and/or functions ofthe units of the network device 1000 are separately used to implementthe corresponding procedures of the network device in the methods inFIG. 1 to FIG. 8. For the purpose of conciseness, details are notdescribed herein again.

Therefore, the network device in this embodiment of this applicationconfigures the plurality of transmission resource chunks for uplinktransmission of the terminal device, sends the frequency domain offsetbetween any two neighboring transmission resource chunks of theplurality of transmission resource chunks to the terminal device, andmay further configure a frequency domain range that can be occupied byat least one transmission resource chunk of the plurality oftransmission resource chunks for the terminal device, so that theterminal device can determine the frequency domain location of theplurality of transmission resource chunks according to the frequencydomain offset and the frequency domain range that can be occupied.Therefore, a configuration manner of the network device is simple, theterminal device may obtain a frequency domain diversity gain, andtransmission resource fragmentation is avoided.

FIG. 17 is a schematic chunk diagram of a terminal device 1100 accordingto an embodiment of this application. As shown in FIG. 17, the terminaldevice 1100 includes: a processor 1110 and a transceiver 1120, where theprocessor 1110 and the transceiver 1120 are connected. Optionally, theterminal device 1100 further includes a memory 1130, where the memory1130 and the processor 1110 are connected. The processor 1110, thememory 1130, and the transceiver 1120 communicate with each other andtransfer and/or control a data signal through an internal connectionpath. The memory 1130 may be configured to store an instruction, and theprocessor 1110 is configured to execute the instruction stored by thememory 1130, to control the transceiver 1120 to send information or asignal. The processor 1110 is configured to determine a resource areaparameter, where the resource area parameter is used to indicate afrequency domain range that can be occupied by at least one transmissionresource chunk of a plurality of transmission resource chunks allocatedby a network device; and determine the plurality of transmissionresource chunks according to the resource area parameter.

Optionally, the transceiver 1120 is configured to receive the resourcearea parameter sent by the terminal device.

Optionally, the transceiver 1120 is configured to receive aconfiguration message sent by the network device, where theconfiguration message is used to indicate the resource area parameter,and the configuration message is at least one of a network broadcastmessage, a network system message, an RRC message, a MAC CE, and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the terminal device 1100 according to thisembodiment of this application may correspond to the terminal device 700in the embodiments of this application, and may correspond to acorresponding entity for performing the method 300 in the embodiments ofthis application. The foregoing and other operations and/or functions ofthe units of the terminal device 1100 are separately used to implementthe corresponding procedures of the terminal device in the methods inFIG. 9 and FIG. 10. For the purpose of conciseness, details are notdescribed herein again.

Therefore, the terminal device in this embodiment of this applicationdetermines the resource area parameter, where the resource areaparameter is used to indicate the frequency domain range that can beoccupied by at least one transmission resource chunk of the plurality oftransmission resource chunks allocated by the network device, anddetermines the plurality of transmission resource chunks in the rangeindicated by the resource area parameter, so that the terminal devicemay perform uplink transmission by using the plurality of transmissionresource chunks, to improve transmission efficiency.

FIG. 18 is a schematic chunk diagram of a network device 1200 accordingto an embodiment of this application. As shown in FIG. 18, the networkdevice 1200 includes: a processor 1210 and a transceiver 1220, where theprocessor 1210 and the transceiver 1220 are connected. Optionally, thenetwork device 1200 further includes a memory 1230, where the memory1230 and the processor 1210 are connected. The processor 1210, thememory 1230, and the transceiver 1220 communicate with each other andtransfer and/or control a data signal through an internal connectionpath. The memory 1230 may be configured to store an instruction, and theprocessor 1210 is configured to execute the instruction stored by thememory 1230, to control the transceiver 1220 to send information or asignal. The processor 1210 is configured to determine a resource areaparameter of a terminal device, where the resource area parameter isused to indicate a frequency domain range that can be occupied by atleast one transmission resource chunk of a plurality of transmissionresource chunks allocated to the terminal device; and the transceiver1220 is configured to send the resource area parameter to the terminaldevice.

Optionally, the transceiver 1220 is configured to send a configurationmessage to the terminal device, where the configuration message is usedto indicate the resource area parameter, and the configuration messageis at least one of a network broadcast message, a network systemmessage, an RRC message, a MAC CE, and DCI.

Optionally, the frequency domain range that can be occupied by the atleast one transmission resource chunk and that is indicated by theresource area parameter is discontinuous.

It should be understood that the network device 1200 according to thisembodiment of this application may correspond to the network device 800in the embodiments of this application, and may correspond to acorresponding entity for performing the method 400 in the embodiments ofthis application. The foregoing and other operations and/or functions ofthe units of the network device 1200 are separately used to implementthe corresponding procedures of the network device in the methods inFIG. 9 and FIG. 10. For the purpose of conciseness, details are notdescribed herein again.

Therefore, the network device in this embodiment of this applicationconfigures the plurality of transmission resource chunks for theterminal device, and sends, to the terminal device, the resource areaparameter used to indicate the frequency domain range that can beoccupied by at least one transmission resource chunk of the plurality oftransmission resource chunks, so that the terminal device can determinethe plurality of transmission resource chunks in the range indicated bythe resource area parameter, and perform uplink transmission by usingthe plurality of transmission resource chunks, to improve transmissionefficiency.

It should be noted that the method embodiments of this application maybe applied to a processor or implemented by a processor. The processormay be an integrated circuit chip having a signal processing capability.In an implementation process, the steps of the foregoing methodembodiments may be implemented by using a hardware integrated logiccircuit in the processor or instructions in a form of software. Theprocessor may be a general-purpose processor, a digital signal processor(DSP), an application-specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA), or other programmable logic devices,discrete gate or transistor logic devices, and discrete hardwarecomponents. The processor may implement or perform the methods, thesteps, and logical chunk diagrams that are disclosed in the embodimentsof this application. The general-purpose processor may be amicroprocessor, or the processor may be any conventional processor orthe like. Steps of the methods disclosed with reference to theembodiments of this application may be directly performed and completedby using a hardware decoding processor, or may be performed andcompleted by using a combination of hardware and a software module inthe decoding processor. The software module may be located in a maturestorage medium in the art, such as a random access memory, a flashmemory, a read-only memory, a programmable read-only memory, anelectrically erasable programmable memory, or a register. The storagemedium is located in the memory, and the processor reads information inthe memory and completes the steps in the foregoing methods incombination with hardware of the processor.

It may be understood that the memory in the embodiments of thisapplication may be a volatile memory or a non-volatile memory, or mayinclude both a volatile memory and a non-volatile memory. Thenon-volatile memory may be a read-only memory (ROM), a programmableread-only memory (PROM), an erasable programmable read-only memory(EPROM), an electrically erasable programmable read-only memory(EEPROM), or a flash. A volatile memory may be a random access memory(RAM), and is used as an external cache. RAMs in many forms such as astatic random access memory (SRAM), a dynamic random access memory(DRAM), a synchronous dynamic random access memory (SDRAM), a doubledata rate synchronous dynamic random access memory (DDR SDRAM), anenhanced synchronous dynamic random access memory (ESDRAM), a synchlinkdynamic random access memory (SLDRAM), and a direct rambus random accessmemory (DR RAM) may be used, which is used as an example but is not alimitative description. It may be understood that the memory in thesystem and method described in this specification intends to include,but is not limited to, these memories and any other memory of a suitabletype.

A person of ordinary skill in the art may be aware that, in combinationwith the examples described in the embodiments disclosed in thisspecification, units and algorithm steps may be implemented byelectronic hardware or a combination of computer software and electronichardware. Whether the functions are performed by hardware or softwaredepends on particular applications and design constraint conditions ofthe technical solutions. A person skilled in the art may use differentmethods to implement the described functions for each particularapplication, but it should not be considered that the implementationgoes beyond the scope of this application.

It may be clearly understood by a person skilled in the art that, forthe purpose of convenient and brief description, for a detailed workingprocess of the foregoing system, apparatus, and unit, reference may bemade to a corresponding process in the foregoing method embodiments, anddetails are not described herein again.

In the several embodiments provided in this application, it should beunderstood that the disclosed system, apparatus, and method may beimplemented in other manners. For example, the described apparatusembodiment is merely an example. For example, the unit division ismerely logical function division and may be other division during actualimplementation. For example, a plurality of units or components may becombined or integrated into another system, or some features may beignored or not performed. In addition, the displayed or discussed mutualcouplings or direct couplings or communication connections may beimplemented by using some interfaces. The indirect couplings orcommunication connections between the apparatuses or units may beimplemented in electronic, mechanical, or other forms.

The units described as separate parts may or may not be physicallyseparate, and the parts displayed as units may or may not be physicalunits, may be located in one position, or may be distributed on aplurality of network units. Some of or all of the units may be selectedaccording to actual needs to achieve the objectives of the solutions ofthe embodiments.

In addition, functional units in the embodiments of this application maybe integrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit.

When the functions are implemented in the form of a software functionalunit and sold or used as an independent product, the functions may bestored in a computer-readable storage medium. Based on such anunderstanding, the technical solutions of this application essentially,or the part contributing to the prior art, or some of the technicalsolutions may be implemented in a form of a software product. Thecomputer software product is stored in a storage medium, and includesseveral instructions for instructing a computer device (which may be apersonal computer, a server, or a network device) to perform all or someof the steps of the methods described in the embodiments of thisapplication. The foregoing storage medium includes: any medium that canstore program code, such as a USB flash drive, a removable hard disk, aread-only memory (ROM), a random access memory (RAM), a magnetic disk,or an optical disc.

The foregoing descriptions are merely specific implementations of thisapplication, but are not intended to limit the protection scope of thisapplication. Any variation or replacement readily figured out by aperson skilled in the art within the technical scope disclosed in thisapplication shall fall within the protection scope of this application.Therefore, the protection scope of this application shall be subject tothe protection scope of the claims.

What is claimed is:
 1. A resource configuration method comprising:determining a frequency domain offset between a plurality oftransmission resource chunks allocated by a network device, wherein thefrequency domain offset is a frequency domain offset between a firsttransmission resource chunk and a second transmission resource chunk,and the first transmission resource chunk and the second transmissionresource chunk are any two consecutive resource chunks on an uplinktransmission in the plurality of transmission resource chunks;determining the plurality of transmission resource chunks according tothe frequency domain offset, wherein the plurality of transmissionresource chunks are configured for a frequency hopping transmission; anddetermining a resource area parameter, wherein the resource areaparameter is used to indicate a frequency domain range that can beoccupied by at least one transmission resource chunk of the plurality oftransmission resource chunks, and the at least one transmission resourcechunk comprises the first transmission resource chunk or the secondtransmission resource chunk; wherein determining the plurality oftransmission resource chunks according to the frequency domain offset,comprises determining the plurality of transmission resource chunksaccording to the frequency domain offset and the resource areaparameter.
 2. The method of claim 1 wherein the frequency hoppingtransmission is a physical uplink shared channel (PUSCH) frequencyhopping transmission.
 3. The method of claim 1 wherein the frequencydomain offset is a difference between a start location of the firsttransmission resource chunk in frequency domain and a start location ofthe second transmission resource chunk in frequency domain.
 4. Themethod of claim 1 wherein: the first transmission resource chunk and thesecond transmission resource chunk separately occupy a subframe or amini-subframe; the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.
 5. Themethod of claim 1 wherein determining a frequency domain offset betweena plurality of transmission resource chunks allocated by a networkdevice comprises: receiving a first configuration message sent by thenetwork device, wherein the first configuration message is used toindicate the frequency domain offset, and the first configurationmessage is at least one of a network broadcast message, a network systemmessage, a Radio Resource Control (RRC) message, a Media Access Controlcontrol element (MAC CE), or downlink control information (DCI).
 6. Themethod of claim 1 wherein, if the frequency domain of the secondtransmission resource chunk exceeds a frequency domain range indicatedby a resource region parameter, the frequency domain that is notexceeded in the frequency domain of the second transmission resourcechunk occupies a first frequency domain position within the frequencydomain range indicated by the resource region parameter, the frequencydomain exceeded in the frequency domain of the second transmissionresource chunk occupies a second frequency domain position within thefrequency domain range indicated by the resource region parameter,wherein the first frequency domain position does not overlap with thesecond frequency domain position.
 7. The method of claim 1 whereindetermining a resource area parameter comprises r receiving a secondconfiguration message sent by the network device, wherein the secondconfiguration message is used to indicate the resource area parameter,and wherein the second configuration message is at least one of anetwork broadcast message, a network system message, a Radio ResourceControl (RRC) message, a Media Access Control control element (MAC CE),or downlink control information (DCI).
 8. A terminal device comprising:a memory configured to store computer-executable instructions; and oneor more processors in communication with the memory and configured toexecute the computer-executable instructions to at least: determine afrequency domain offset between a plurality of transmission resourcechunks allocated by a network device, wherein the frequency domainoffset is a frequency domain offset between a first transmissionresource chunk and a second transmission resource chunk, and the firsttransmission resource chunk and the second transmission resource chunkare any two consecutive resource chunks on an uplink transmission in theplurality of transmission resource chunks; determine the plurality oftransmission resource chunks according to the frequency domain offset,wherein the plurality of transmission resource chunks are configured fora frequency hopping transmission; and determine a resource areaparameter, wherein the resource area parameter is used to indicate afrequency domain range that can be occupied by at least one transmissionresource chunk of the plurality of transmission resource chunks, andwherein the at least one transmission resource chunk comprises the firsttransmission resource chunk or the second transmission resource chunk;wherein determining the plurality of transmission resource chunksaccording to the frequency domain offset comprises determining theplurality of transmission resource chunks according to the frequencydomain offset and the resource area parameter.
 9. The terminal device ofclaim 8, wherein the frequency hopping transmission is a physical uplinkshared channel (PUSCH) frequency hopping transmission.
 10. The terminaldevice of claim 8 wherein the frequency domain offset is a differencebetween a start location of the first transmission resource chunk infrequency domain and a start location of the second transmissionresource chunk in frequency domain.
 11. The terminal device of claim 8wherein: the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.
 12. Theterminal device of claim 8 wherein the terminal device further comprisesa communications interface, configured to receive a first configurationmessage sent by the network device, wherein the first configurationmessage is used to indicate the frequency domain offset, and wherein thefirst configuration message is at least one of a network broadcastmessage, a network system message, a Radio Resource Control (RRC)message, a Media Access Control control element (MAC CE), or downlinkcontrol information (DCI).
 13. The terminal device of claim 8 wherein,if the frequency domain of the second transmission resource chunkexceeds a frequency domain range indicated by a resource regionparameter, the frequency domain that is not exceeded in the frequencydomain of the second transmission resource chunk occupies a firstfrequency domain position within the frequency domain range indicated bythe resource region parameter, the frequency domain exceeded in thefrequency domain of the second transmission resource chunk occupies asecond frequency domain position within the frequency domain rangeindicated by the resource region parameter, wherein the first frequencydomain position does not overlap with the second frequency domainposition.
 14. The terminal device of claim 8 wherein the terminal devicefurther comprises a communications interface configured to receive asecond configuration message sent by the network device, wherein thesecond configuration message is used to indicate the resource areaparameter, and wherein the second configuration message is at least oneof a network broadcast message, a network system message, an RRCmessage, a MAC CE, or DCI.
 15. A non-transitory computer-readablestorage medium storing computer-executable instructions that, whenexecuted by a computer system, configure the computer system to performoperations comprising: determining a frequency domain offset between aplurality of transmission resource chunks allocated by a network device,wherein the frequency domain offset is a frequency domain offset betweena first transmission resource chunk and a second transmission resourcechunk, and the first transmission resource chunk and the secondtransmission resource chunk are any two consecutive resource chunks onan uplink transmission in the plurality of transmission resource chunks;determining the plurality of transmission resource chunks according tothe frequency domain offset, wherein the plurality of transmissionresource chunks are configured for a frequency hopping transmission; andif the frequency domain of the second transmission resource chunkexceeds a frequency domain range indicated by a resource regionparameter, the frequency domain that is not exceeded in the frequencydomain of the second transmission resource chunk occupies a firstfrequency domain position within the frequency domain range indicated bythe resource region parameter, the frequency domain exceeded in thefrequency domain of the second transmission resource chunk occupies asecond frequency domain position within the frequency domain rangeindicated by the resource region parameter, wherein the first frequencydomain position does not overlap with the second frequency domainposition.
 16. The non-transitory computer-readable storage medium ofclaim 15 wherein the frequency hopping transmission is a physical uplinkshared channel (PUSCH) frequency hopping transmission.
 17. Thenon-transitory computer-readable storage medium of claim 15 wherein thefrequency domain offset is a difference between a start location of thefirst transmission resource chunk in frequency domain and a startlocation of the second transmission resource chunk in frequency domain.18. The non-transitory computer-readable storage medium of claim 15wherein: the first transmission resource chunk and the secondtransmission resource chunk separately occupy a subframe or amini-subframe; the first transmission resource chunk occupies a firstpart of a subframe and the second transmission resource chunk occupies asecond part of the subframe; or the first transmission resource chunkoccupies a first part of a mini-subframe and the second transmissionresource chunk occupies a second part of the mini-subframe.
 19. Thenon-transitory computer-readable storage medium of claim 15 whereindetermining a frequency domain offset between a plurality oftransmission resource chunks allocated by a network device comprisesreceiving a first configuration message sent by the network device,wherein the first configuration message is used to indicate thefrequency domain offset, and the first configuration message is at leastone of a network broadcast message, a network system message, a RadioResource Control (RRC) message, a Media Access Control control element(MAC CE), or downlink control information (DCI).